| Package | ForgePatientChart.0830 |
| Type | StructureDefinition |
| Id | Id |
| FHIR Version | R4 |
| Source | https://simplifier.net/resolve?scope=ForgePatientChart.0830@0.1.0&canonical=http://telus.com/fhir/patientChart/StructureDefinition/profile-procedure |
| Url | http://telus.com/fhir/patientChart/StructureDefinition/profile-procedure |
| Status | draft |
| Name | Procedure |
| Experimental | False |
| Authority | hl7 |
| Type | Procedure |
| Kind | resource |
No resources found
| ValueSet | |
http://fhir.infoway-inforoute.ca/io/psca/ValueSet/ICD9CM  | ICD-9 CM All Concepts |
| https://fhir.infoway-inforoute.ca/ValueSet/procedurecode | Procedure Code |
| http://hl7.org/fhir/uv/ips/ValueSet/absent-or-unknown-procedures-uv-ips | Absent or Unknown Procedures - IPS |
FHIR{
"resourceType" : "StructureDefinition",
"url" : "http://telus.com/fhir/patientChart/StructureDefinition/profile-procedure",
"name" : "Procedure",
"status" : "draft",
"fhirVersion" : "4.0.1",
"kind" : "resource",
"abstract" : false,
"type" : "Procedure",
"baseDefinition" : "http://hl7.org/fhir/StructureDefinition/Procedure",
"derivation" : "constraint",
"differential" : {
"element" : [
{
"id" : "Procedure.id",
"path" : "Procedure.id",
"mustSupport" : true
},
{
"id" : "Procedure.meta",
"path" : "Procedure.meta",
"mustSupport" : true
},
{
"id" : "Procedure.meta.lastUpdated",
"path" : "Procedure.meta.lastUpdated",
"mustSupport" : true
},
{
"id" : "Procedure.meta.source",
"path" : "Procedure.meta.source",
"mustSupport" : true
},
{
"id" : "Procedure.meta.profile",
"path" : "Procedure.meta.profile",
"mustSupport" : true
},
{
"id" : "Procedure.text",
"path" : "Procedure.text",
"mustSupport" : true
},
{
"id" : "Procedure.status",
"path" : "Procedure.status",
"comment" : "Usage Note: Most of the time, the status will be completed as they are typically recorded after the procedure has completed.\r\n\r\nThe \"unknown\" code is not to be used to convey other statuses. The \"unknown\" code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the procedure.\r\n\r\n\n\nThis element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.",
"mustSupport" : true
},
{
"id" : "Procedure.code",
"path" : "Procedure.code",
"comment" : "Conformance Rule: The local code must always be specified where present. If a SNOMED code is present, this must also be sent.\r\n\r\nAlignment PS-ON: 1..1 Must support SNOMED coding; this is very often not used by the physician. \r\nAlignment PS-ON: In situations where the EMR cannot distinguish between no-known and no information about patient procedures, then the code for no information should be used. In the instance where a patient is KNOWN to have no procedures, the no-known code should be used.\r\r\n\r\nNot all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.",
"mustSupport" : true
},
{
"id" : "Procedure.code.coding",
"path" : "Procedure.code.coding",
"slicing" : {
"discriminator" : [
{
"type" : "value",
"path" : "system"
}
],
"rules" : "open"
},
"mustSupport" : true
},
{
"id" : "Procedure.code.coding.system",
"path" : "Procedure.code.coding.system",
"min" : 1,
"fixedUri" : "http://snomed.info/sct",
"mustSupport" : true
},
{
"id" : "Procedure.code.coding.code",
"path" : "Procedure.code.coding.code",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Procedure.code.coding.display",
"path" : "Procedure.code.coding.display",
"mustSupport" : true
},
{
"id" : "Procedure.code.coding:SCTCA",
"path" : "Procedure.code.coding",
"sliceName" : "SCTCA",
"comment" : "CoreCA: While the IPS-UV specification considers this a Must Support element, some systems will not have the ability to support codings for every codeableConcept, further feedback is required on whether these systems are still expected to be able to demonstrate they can construct this element when developing the patient summary instance. Implementors that support codings should still send the codings for codeable concepts if they are available and receivers should not produce failures or rejections if codings are included in the patient summary in the first release (a base tenet of FHIR). Additionally vendors should expect that some jurisdictions may further constrain support of this element within the context of their own jurisdictional content\r\n\r\nCodes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.",
"binding" : {
"strength" : "required",
"valueSet" : "https://fhir.infoway-inforoute.ca/ValueSet/procedurecode"
}
},
{
"id" : "Procedure.code.coding:SCTCA.system",
"path" : "Procedure.code.coding.system",
"mustSupport" : true
},
{
"id" : "Procedure.code.coding:SCTCA.code",
"path" : "Procedure.code.coding.code",
"mustSupport" : true
},
{
"id" : "Procedure.code.coding:codeICD9CM",
"path" : "Procedure.code.coding",
"sliceName" : "codeICD9CM",
"definition" : "This slice reflects that ICD-9 CM is used in some Canadian jurisdictions for procedures. While SNOMED-CT CA is the preferred code system for this element, implementers may encounter ICD-9 CM codes in some circumstances or jurisdictions. Note: Implementers should be cautioned that ICD-9 CM is considered a legacy terminology that is no longer maintained by the organization that developed it.",
"comment" : "Core-CA\r\n\r\nCodes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.",
"binding" : {
"strength" : "required",
"valueSet" : "http://fhir.infoway-inforoute.ca/io/psca/ValueSet/ICD9CM"
}
},
{
"id" : "Procedure.code.coding:codeICD9CM.system",
"path" : "Procedure.code.coding.system",
"fixedUri" : "http://terminology.hl7.org/CodeSystem/icd9cm",
"mustSupport" : true
},
{
"id" : "Procedure.code.coding:codeICD9CM.code",
"path" : "Procedure.code.coding.code",
"mustSupport" : true
},
{
"id" : "Procedure.code.coding:absentOrUnknownProcedure",
"path" : "Procedure.code.coding",
"sliceName" : "absentOrUnknownProcedure",
"comment" : "Core-CA - While the IPS-UV specification considers this a Must Support element, some systems will not have the ability to support codings for every codeableConcept, further feedback is required on whether these systems are still expected to be able to demonstrate they can construct this element when developing the patient summary instance. Implementors that support codings should still send the codings for codeable concepts if they are available and receivers should not produce failures or rejections if codings are included in the patient summary in the first release (a base tenet of FHIR). Additionally vendors should expect that some jurisdictions may further constrain support of this element within the context of their own jurisdictional content\r\n\r\nCodes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.",
"binding" : {
"strength" : "required",
"valueSet" : "http://hl7.org/fhir/uv/ips/ValueSet/absent-or-unknown-procedures-uv-ips"
}
},
{
"id" : "Procedure.code.coding:absentOrUnknownProcedure.system",
"path" : "Procedure.code.coding.system",
"fixedUri" : "http://hl7.org/fhir/uv/ips/CodeSystem/absent-unknown-uv-ips",
"mustSupport" : true
},
{
"id" : "Procedure.code.coding:absentOrUnknownProcedure.code",
"path" : "Procedure.code.coding.code",
"mustSupport" : true
},
{
"id" : "Procedure.code.text",
"path" : "Procedure.code.text",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Procedure.subject",
"path" : "Procedure.subject",
"mustSupport" : true
},
{
"id" : "Procedure.subject.reference",
"path" : "Procedure.subject.reference",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Procedure.subject.display",
"path" : "Procedure.subject.display",
"mustSupport" : true
},
{
"id" : "Procedure.performed[x]",
"path" : "Procedure.performed[x]",
"comment" : "Core-CA - this is mandatory in Core-CA and in order to align, it must be specified here when known.\r\n\r\nUsage Note: This may not be recorded in the EMR in some cases, eg the patient is taking CBT and has not provided specific dates. In this case, the string may be used to state \"unknown\" at time of export.\r\n\r\nAge is generally used when the patient reports an age at which the procedure was performed. Range is generally used when the patient reports an age range when the procedure was performed, such as sometime between 20-25 years old. dateTime supports a range of precision due to some procedures being reported as past procedures that might not have millisecond precision while other procedures performed and documented during the encounter might have more precise UTC timestamps with timezone.",
"min" : 1,
"mustSupport" : true
}
]
},
"text" : {
}
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.